Fix GPG verify path for staged release artifacts#1582
Merged
tuhaihe merged 1 commit intoapache:mainfrom Feb 28, 2026
Merged
Conversation
tuhaihe
force-pushed
the
update-rc-shell
branch
from
b847226 to
0c79843
Compare
reshke
approved these changes
Feb 27, 2026
leborchuk
approved these changes
Feb 27, 2026
tuhaihe
force-pushed
the
update-rc-shell
branch
from
0c79843 to
da1919a
Compare
Use absolute artifact paths in the GPG verification step of
devops/release/cloudberry-release.sh.
Previously, the script verified SHA-512 using an absolute path but
called `gpg --verify` with relative file names. When running with
`--repo` from a different working directory, this could fail with
"No such file or directory" even though the `.asc` file existed in
the artifacts directory.
This change aligns the GPG verify command with the SHA-512 check by
verifying:
$ARTIFACTS_DIR/${TAR_NAME}.asc
against:
$ARTIFACTS_DIR/$TAR_NAME
No behavior change for successful local runs besides making path
resolution robust.
tuhaihe
force-pushed
the
update-rc-shell
branch
from
da1919a to
0dd2bd0
Compare
Member
Author
|
Before: =================================================================
>> Verifying GPG Signature (/Users/djwang/workdir/artifacts/apache-cloudberry-2.1.0-incubating-rc2-src.tar.gz.asc) Release Artifact
=================================================================
gpg: can't open 'apache-cloudberry-2.1.0-incubating-rc2-src.tar.gz.asc': No such file or directory
gpg: verify signatures failed: No such file or directoryAfter: =================================================================
>> Verifying GPG Signature (/Users/djwang/workdir/artifacts/apache-cloudberry-2.1.0-incubating-rc2-src.tar.gz.asc) Release Artifact
=================================================================
gpg: Signature made Sat Feb 28 16:13:07 2026 CST
gpg: using RSA key 9A36AA272348A207E193A49C500708B75754FB7C
gpg: Good signature from "Dianjin Wang (for apache cloudberry release) <djwang@apache.org>" [ultimate]
Press Enter or type y/yes to continue, or 'n' to exit: y
=================================================================
>> Release candidate for 2.1.0-incubating-rc2 staged successfully
================================================================= |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use absolute artifact paths in the GPG verification step of devops/release/cloudberry-release.sh.
Previously, the script verified SHA-512 using an absolute path but called
gpg --verifywith relative file names. When running with--repofrom a different working directory, this could fail with "No such file or directory" even though the.ascfile existed in the artifacts directory.This change aligns the GPG verify command with the SHA-512 check by verifying:
$ARTIFACTS_DIR/$ {TAR_NAME}.asc
against:
$ARTIFACTS_DIR/$TAR_NAME
No behavior change for successful local runs besides making path resolution robust.
Fixes #ISSUE_Number
What does this PR do?
Type of Change
Breaking Changes
Test Plan
make installcheckmake -C src/test installcheck-cbdb-parallelImpact
Performance:
User-facing changes:
Dependencies:
Checklist
Additional Context
CI Skip Instructions